System and method for ongoing supporting a procurement and accounts payable system

ABSTRACT

A system for deploying to a client accounting installation a general procurement and accounts payable application specifically configured for the client by an enterprise includes a database server for (1) maintaining on a storage device a database of templates describing procedures for assessing, preparing, developing, deploying and supporting the application, and for (2) serving these templates to team members operating web-enabled terminals for coordinating, recording and tracking team activities with respect to the application while generating a description for adapting a front end server and an accounting system server to the requirements of the client.

CROSS REFERENCES TO RELATED APPLICATIONS

U.S. patent applications Ser. No. 09/444,257, entitled “System andMethod for Assessing a Procurement and Accounts Payable System”, Ser.No. 09/444,254, entitled “System and Method for Project Preparing aProcurement and Accounts Payable Process”, Ser. No. 09/444,255, entitled“System and Method for Project Designing and Developing a Procurementand Accounts Payable Process”, and Ser. No. 09/444,253, entitled “Systemand Method for Deploying a Procurement and Accounts Payable Process”filed concurrently herewith, are assigned to the same assignee hereofand contain subject matter related, in certain respect, to thee subjectmatter of the present application. The above-identified patentapplications are incorporated herein by reference.

BACKGROUND OF THE INVENTION

1. Technical Field of the Invention

This invention pertains to the implementation of a procurement andaccounts payable system or application. More particularly, it relates toa system and method for assessing, preparing, designing and developing,deploying, and supporting a general procurement and accounts payablesystem using electronic requisitions.

2. Background Art

A services company may be very good at implementing informationtechnology (IT) solutions. However, as customer engagements increase,the ability of company to execute numerous engagements on time andwithin budget with quality becomes more difficult.

Today there exist many different software packages that perform projectmanagement and classes that teach methodologies for implementingsolutions that involve information technology and services. However,there is no process that combines these activities along with anevaluation of a client's general procurement (GP) and accounts payable(AP) system, or application, into one package while providing detailedimplementation instructions along with templates for completing themajor deliverables required over the course of the project. Templates,may be used herein as an equivalent term for page, form, or document asused in connection with Lotus Notes. In Lotus Notes, a page is adatabase design element that displays information; a form, like a page,displays information and also can be used to collect information; anddocuments are the elements that store information in the database. Auser is presented a form including fields for entering information. Whenthe user fills out the information and saves it, the information issaved in the data base as a document. When a user opens the document,the document uses the form as a template to provide the structure fordisplaying the data or information. Fields store data of various types,including text, dialog list, rich text, and so forth.

Scalability of engagements is a known problem, the most common solutionto which is to increase the number of persons involved. Experience hasshown that this increase results in customer dissatisfaction due toinadequate gathering of requirements, poorly trained implementationteams, missed schedules, increased costs, and lower quality.

It is characteristic of general procurement and accounts payable systemsthat no two are identical, and may differ even within wholly ownedsubsidiaries of a single corporation.

Consequently, there is a need in the art for a system and method forevaluating a potential client system and for adapting a generalprocurement and accounts payable system to the requirements of each ofmany potential clients. Further, there is a need for a system and methodfor evaluating a potential client system and for adapting a generalprocurement and accounts payable system to the requirements of each ofmany potential clients which can be licensed to third party providerstogether with a system and method for monitoring and assuring thequality of services provided by those service providers.

There is a need in the art for an integrated system for assessing,preparing, designing and developing, deploying, and supporting aprocurement and accounts payable system using electronic requisitions.

During project assessment, typically potential customers are contactedand evaluated by a marketing team that then recommends a productsolution from their menu. There is no integration of Technical TeamLeaders and Transition Management as key components of the installation.There is also limited to no flexibility to customize the product for thecustomer.

There is a large body of work on project planning in industry. Whilethey are all more or less adequate, they do not provide thecomprehensive integration of the client and supplier teams, TransitionManagement, and Quality required to accomplish a particular customer'sgoals.

Like project planning, project design and development processes are wellknown in industry. They usually consist of a project manager or teamleader that manages the implementation of a project plan and interfaceswith the client.

Deployment or implementation of a project is, again, a very standardoperation. As the project plan steps are completed, they are usuallyheld in queue until all necessary activities reach a point where thesolution can be “turned on”.

All projects have close out functions that wrap up the end of theproject. However, they do not provide for continuing support across themultitude of functions that have been used to provide the customer witha solution.

It is an objective of the invention to provide a system and method forevaluating a client's general procurement and accounts payable (GP/AP)system.

It is an object of the invention to provide an optimized solution forout-sourcing procurement of goods and services.

It is an object of the invention to provide a system and method fortraining service providers.

It is an object of the invention to provide a system and method formanaging service providers to assure quality of service.

It is an object of the invention to provide a system and method formanaging a project.

It is an object of the invention to provide an optimized generalprocurement and accounts payable system characterized by lower costs, apaperless process, and more comprehensive service with a shorter cycletime.

SUMMARY OF THE INVENTION

A system for providing ongoing support for a general procurement andaccounts payable application includes a server; a storage deviceconnected to the server; a plurality of team terminals; and acommunication link interconnecting the server and terminals. The serveris operable for (1) maintaining a database of templates on the storagedevice describing procedures for supporting the application and (2)serving the templates to team members operating the terminals forcoordinating, recording, and tracking team activities executing theprocedures with respect to supporting the application. These proceduresinclude user education, survey and quality auditing tasks.

A method for providing ongoing support for a general procurement andaccounts payable application of a customer of an enterprise includesmaintaining a database of templates describing procedures for supportingan operational general procurement and accounts payable system; andoperating a plurality of web-enabled user terminals to access via aserver the database for coordinating tasks by a plurality of enterpriseteams implementing the procedures. The procedures include usereducation, survey and quality auditing tasks.

In accordance with an aspect of the invention, there is provided acomputer program product configured to be operable for providing ongoingsupport for a general procurement and accounts payable application of acustomer of an enterprise.

Other features and advantages of this invention will become apparentfrom the following detailed description of the presently preferredembodiment of the invention, taken in conjunction with the accompanyingdrawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a high level block diagram of a general procurement andaccounts payable development and implementation system in accordancewith a preferred embodiment of the invention.

FIG. 2 is a block diagram illustrating team relationships within thegeneral procurement and accounts payable (GP/AP) development andimplementation system of a preferred embodiment of the invention.

FIGS. 3A through 3H and 3J through 3M, arranged as shown in FIG. 3, area flow diagram of the assessment, preparation, development, deploymentand support phases of the method of a preferred embodiment of theinvention.

FIG. 4 represents a terminal display of a playbook summary view.

FIG. 5 illustrates a terminal display of the template presented by theserver at a user terminal of FIG. 1 in response to selection by a userof “create a summary task” from the playbook summary view.

FIG. 6 illustrates a terminal display of the template presented by theserver at a user terminal of FIG. 1 in response to selection by a userof “create a detailed task” from the playbook summary view.

FIGS. 5 and 6 also illustrate fields collected in the database andselectively displayed at user terminals of FIG. 1 for each summary anddetail task, respectively, of a GP/AP system for a particular customeror project.

BEST MODE FOR CARRYING OUT THE INVENTION

Referring to FIG. 1, in accordance with the preferred embodiment of theinvention, intranet communication facilities interconnect a plurality ofteam member terminals 64, zero or more service provider terminals 66,and client (also referred to as customer) terminals 68, and a server 62,preferably a Lotus Notes server.

Server 62 references and maintains playbook database 70. Database (alsoreferred to as the playbook, or playbook database) 70 is provided forimplementing procurement and accounts payable systems. This playbook 70defines implementation steps and templates for creating the manyrequired deliverables and project management functions. These functionsinclude start and end dates, effort, duration, and so forth. Thisplaybook also provides the steps and templates for training serviceproviders 66 and serves as the repository for completed templates and asa source for auditing the performance of the service providers. As usedherein, unless otherwise apparent from the context, system andapplications are used to refer to hardware, software, procedures,instructional materials, and so forth, for implementing a generalprocurement and accounts payable process.

Also attached to intranet 60 are requisition and catalog (Req/Cat)servers 80. Server 80 functions as a front end server to accountingsystem server 82, and is connected to a file of vendor catalogs andcontracts 72, to a client (customer) host system 74, and through afirewall to SAP servers 82. SAP server 82 is an accounting driver forthe procurement and accounts payable (A/P) system of the customer. SAPservers 82 are connected to supplier systems 84, to a customer datawarehouse 78, and to customer ledger and accounts payable systems 86,88.

During the operational phase of a completed and functioning system, acustomer (aka end user, or client) 98 enters requisitions via theintranet to server 80. Server 80 accesses client host system 74 forpricing, reports, etc., and vendor catalogs and contracts 72 to gatherinformation needed by SAP servers 82 to generate purchase orders orrequests for quotes (RFQs) to supplier 84, to update data warehouse 78,client ledger 86, and client accounts payable 88 systems. Warehouse 78stores client data maintained by the supplier of the Req/Cat and generalprocurement system, which supplier may be the primary enterprise (aprimary services organization, such as the IBM Corporation) with controlof the design and implementation of the system, or a contractor of theenterprise qualified as a third party service provider.

In operation, during presales, assessment, preparation, development,deployment and support stages, team members 64, access database 70 viaintranet 60 and server 62 to create a playbook including a detaileddescription of an accounts payable and Req/Cat system for a particularcustomer (aka client). This description is then used to personalizeReq/Cat servers 80 and SAP servers 82 for the customer installation.During operation, a user 98 accesses Req/Cat server 80 via intranet 60to enter a requisition or to query the status of previously enteredrequisition. When entering a requisition, Req/Cat responds to end user98 with a form to complete. Req/Cat 80 accesses SAP server 82 throughthe firewall with the requisition or request for status. SAP server 82,responsive to a requisition, issues a purchase order or request forquote to supplier 84, and updates accounts payable 88 and ledger 86, asrequired through the normal procurement and accounting processimplemented on behalf of the customer.

Referring to FIG. 2, the various departments and individualsrepresenting team members 64 include business office 120, architecture122, education and training 124, project manager 126, Req/Catdevelopment 128, business process design 112, electronic datainterchange (EDI) 114, application development 116, informationtechnology 130, business controls 132, procurement process 134,transition management 136, SAP development 138, marketing 118, generalprocurement operations 98, and support management 96. Each of thesedepartments and individuals perform various rolls and functions duringthe life of the project from assessment through deployment and use, aswill be more fully described hereafter in connection with FIG. 3.

Referring to FIG. 3, in accordance with the preferred embodiment of themethod of the invention, assessment 101, preparation 102, development103, deployment 104 and support 105 stages are executed to design,implement, and use a general procurement and accounts payable (GP/AP)system for a customer. Through these stages 101-105, procedures andmethods are provided for seamlessly integrating all aspects of a totalGP/AP system, including creating an electronic purchase requisition forgoods and services with flexible approval functions, through invoicingand payment.

Further in accordance with the preferred embodiment of the invention,there is provided a web enabled delivery system.

Further in accordance with the preferred embodiment of the invention,there is provided a system and method for auditing service provideractivities without being on site.

High level summary tasks implemented by playbook 70 database includebusiness controls, information technology, SAP, communication, process,testing, configuration, project management, transition management,education and training, requisition and catalog (Req/Cat). Each of thesesummary tasks, as well as the drill-down (aka subsidiary) tasksimplementing the details of each, may be accessed by team members 64 andservice provider 66s within the playbook database 70.

Referring to FIG. 4, the playbook summary view 400 is illustrated. View400 includes a title bar 402; pull down menu tabs file 404, edit 406,view 408, create 410, actions 412, window 414, help 416; create asummary task selection button 420, create a detailed task button 422, afolders and views section 424, and a task title display and selectionarea 426 which also includes a by column 436 and a status column 438with an entry for each task displayed in area 426. With by categorybutton 430 and all tasks button 432 selected, all tasks 434 ishighlighted and display 426 presents a listing of tasks organized bycategory.

Referring to FIG. 5, the summary task template 440 presented to the userupon selection of create a summary task 420 is illustrated. As will bedescribed hereafter, there are two flavors of template 440, one formajor operations, and one for major steps within each major operation.Referring to FIG. 6, the detail task template 520 presented to the userupon selection of create a detailed task 422 is illustrated.

Selection of create summary task 420 presents a first summary tasktemplate 440 that used to design and describe a high level summary taskfor one of the playbook operations. In a preferred embodiment of theinvention, there are thirteen such high level summary tasks, includingassessment, business controls, configuration, education, image,information technology (I/T), marketing, process, project management,requisition and catalog (req/cat), SAP, testing, and transitionmanagement. The summary and detail tasks within these high level summarytasks are further organized into five major processing segments:assessment 101, project preparation 102, project design and development103, deployment 104, and ongoing support 105. A high level summary taskprovides a summary of the inputs to the task, and of the output(deliverables) after all detailed tasks are completed. There two levels,or templates for summary tasks: one for major operations, the second formajor steps within each operation.

Activation of create a detail task 422 presents to the user a thirdtemplate 520 which is used to summarize the detailed tasks for eachmajor step of a summary task.

The first and second templates 440 are almost identical. They includethe fields set forth in Tables 1 and 2. Third template 520 contents aresummarized in Table 3.

TABLE 1 SUMMARY TASK TEMPLATES PART 1 SECTION 1: CREATION STATUSCategory 444: Categories include education, req/cat development, SAPdevelopment, transformation management, architecture, procurementprocess. Team 446: Specific project team responsible for this task.Offering type 448: Kind of product being brought to client: req/catonly, SAP only, and req/cat and SAP. Stage 450: The stages areassessment 101, project preparation 102, project development 103,deployment 104, and support 105. Doc owned by 452: Team 140 owner ofdocument, the designer of this one template. The teams 140 are thoseillustrated in FIG. 2. Doc created by 454: Author of this one template.Dev status 456: Approval status: first draft, final edit, finalapproval, etc. Only owner 452 can change this status. Only the owner 452can approve the content of this template (task). SECTION 2: IMPORTANCEBUTTONS Education 462: Represents a combination of things, including (1)does someone need to be taught how to do this task, (2) is it somethingthat should be included in the education package to the customer.Certification 464: Indicates whether or not an implementer of this task(ie, service provider) must be certified. Auditable 466: Indicateswhether or not it is a task that Enterprise would be able to or needs toaudit performance by the implementer/service provider Milestone 468:Indicates if this task is a critical accomplishment in the path ofcompleting the implementation of the offering type. Critical path 470:Indicates if this is a task that must be completed in order to advanceto the next task in order to complete the offering type, and can changeduring the course of the project as tasks are completed and the overallenvironment changes. SECTION 3: IMPLEMENTATION Task order 472: A numberassigned to a detailed task that shows its order under the summary task.% complete 474: An estimate of how complete is this task document in itsdevelopment for a particular customer. Executed by 458: Name of serviceprovider (eg., Enterprise, or some Enterprise partner). Performed by460: Technical team responsible for doing this task. Priority 476: High,medium, low priority, based on whether this task is in critical path,and whether or not it needs to be done in support of some subsequenttask. Work effort 478: Estimated time required to complete this task.Sequence 480: A number assigned to a summary task that shows its orderunder a higher level task. Task status 482: Represents how far theservice provider has progressed in its implementation of this task. Thisis rolled up to Lotus Notes database 70 to enable the owner to trackprogress of the service providers during the audit phase.

Table 2 sets forth the template 440 fields which may vary betweentemplates, including those for major operations and major steps withinan operation.

TABLE 2 SUMMARY TASK TEMPLATES PART 2 SECTION 4: SUMMARY TASK DETAILSDescription 490: High level summary description of major operations orsteps. Assumptions 492: What if any assumptions apply. Prerequisites494: Tasks that must be completed before this task can complete.Critical success factors 496: Description of tools, techniques,relationships, understandings, technical and relationship skills andcommitments, knowledge base of team and customer, and so forth, neededto accomplish this task. Deliverables 498: Expected output of this task.SECTION 5: APPROVALS Task approver 500: Identity of approvers.Notification date 502: Date approvers notified. Request approval 504:Electronic signature of approval. SECTION 6: PROJECT REFERENCE Commentsand dialog 506: General comments (open season). Deliverable checklist408: Checklist of deliverables. Approval status 510: List of approversof this document and status of their approval. Edit history 512: Listingof persons who have modified this document during its preparation(service provider is not allowed to change these task descriptions.)

TABLE 3 DETAIL TASK TEMPLATE SECTION 1: CREATION STATUS SECTION 2:IMPORTANCE BUTTONS SECTION 3: IMPLEMENTATION Sections 1, 2 and 3 are thesame as for templates 440, with the addition of: Support resources 524:People needed to support completion of this task. Assigned to 526:Person executing this task. SECTION 4: DETAIL TASK DETAILS Description490: Description of this task. Prerequisites 494: Tasks that must becompleted before this task can complete. Task steps 528: Specificdetailed steps that need to be accomplished to complete the task.Analysis 540: A description of what needs to be analyzed to come up withthe right answer for the customer. (The resulting output will varydepending upon the results of the analysis - but this document doesn'tchange as a result of the analysis). Deliverables 530: Expected outputof the task. Methodology attachments 532: Potential attachments, may beblank: anything from presentation charts, to questionnaires, toarchitecture charts - depends upon the task. SECTION 5: PROJECTREFERENCE AREA Comments & Dialog 506: Comments. Deliverable Checklist508: Checklist, attachment listing (other than method attachments,supra). Approval status 510: List of approvers and the status of theirapproval (with respect to approval of this document, not of theimplementation of the task, which is handled by the audit process). Edithistory 512: Listing of persons who have modified this document duringits preparation (service provider is not allowed to change these taskdescriptions.)

Database 70 at server 62 includes all summary and detail tasks templateswhich have been completed in a set for a particular customer. An initialset of the tasks listed in Table 4 is provided for each customer, butduring project implementation phases 101-105, these are configured orpersonalized to the customer.

While many summary and detailed tasks of Table 4 do not appear in theflow chart of FIGS. 3A-3M, those selected illustrate a flow from startto finish across the five major stages—and form a representative, if notcritical, path through them. As shown in FIGS. 3, and 3A-3M, thetransitions between stages 100-105 are, in some instances, blurred and aparticular task may be allocated to either or both of two of thesestages.

In each stage, the key to success is the integration through the use ofthe templates of the groups (FIG. 2) and activities (Table 4, bothsummary tasks and detail tasks.) Also, an important aspect of theinvention is the method provided across the five stages (FIG. 3) foreffecting a transition from a legacy process, including hardware,software, work procedures and human resources, to a new process.

Table 4 is a chart of summary and detail tasks, pursuant to a particularembodiment of the invention, available for presentation in display area426 of playbook summary view 400 upon selection of button 432. Selectionby a user in display area 426 of a task designated with two or threealpha-numeric reference numerals P1, P11, P12, . . . , results indisplay of a template 440 personalized to the summary task, andselection of a task designated with four or more alpha-numeric referencenumerals P111, P112, . . . , result in display of a template 520personalized to the detail task. A user with appropriate authority maythen view, correct, update, approve or otherwise modify the displayedtask. The names of the detail tasks set forth broadly the functions ormethod steps performed in implementing the superior summary task. InTable 4, each summary task is identified in the first column by thestage 100-105 to which it pertains, in the second column by a taskidentifier P11, P12, . . . , and, for selected tasks, in the thirdcolumn by the process step (150, . . . , 354 in FIGS. 3A-3M) to which itpertains. In general (with very few exceptions), a detail task pertainsto the same stage 100-105 as its summary task.

TABLE 4 CHART OF SUMMARY AND DETAIL TASKS Task ID Summary Tasks StageStep Detail Tasks FOLDERS AND VIEWS BY CATEGORY ALL TASKS P1 ASSESSMENT101 P11 Perform customer service offering assessment 101 P111 174Perform customer business assessment 101 P112 Perform customer businessassessment e-Req/Cat 101 P113 Develop workshop management plan 101 P114Develop workshop management plan e- Req/Cat 101 P115 Review findingsfrom marketing procurement consulting engagement 101 P116 Reviewfindings from marketing procurement consulting engagement e-Req/Cat 101P117 176 Formulate workshop approach 101 P118 Formulate workshopapproach e- Req/Cat 101 P119 Prepare for workshop 101 P11A Prepare forworkshop e-req/Cat 101 P12 178 Introduce recommend service offering tocustomer 101 P121 Present service offering to customer (performworkshop) 101 P122 Present service offering to customer (performworkshop) e- Req/Cat 101 P123 Formulate proposal approach 101 P124Formulate proposal approach e- Req/Cat 101 P13 Create proposal andcontract 101 P131 Develop and cost proposal 101 P132 Develop and costproposal e-Req/Cat 101 P133 Draft and price customer contract 101 P134Draft and price customer contract e-Req/Cat P2 BUSINESS CONTROLS 103 P21Business control requirements 103 P211 290 Confirm business controlsrequirements 103 P212 Confirm separation of duties (SOD) requirements104 P213 292 Conduct ASCA self-assessment 104 P214 Risk assessment 104P215 224, Conduct ASCA/business controls 294 review 102 P2151 Confirmimage production system management strategy P3 CONFIGURATION 103 P31 320Conduct Req/Cat functional detailed fit gap analysis 103 P311 ConfirmReq/Cat organizational hierarchy 103 P312 Define the Req/Cat functionaldetailed fit 103 P313 Resolve functional gaps for Req/Cat 103 P32 324Configure Req/Cat offering 103 P321 Confirm and refine “Ives TeamStudio” for code tracking 103 P322 Confirm and refine Req/Cat initialsettings and organizational structure 103 P323 Confirm and refineReq/Cat authorizations 103 P324 Refine and validate final Req/Catconfiguration 103 P33 Customize Req/Cat offering 103 P331 Validate andcustomize Req/Cat core application change request 103 P332 Refine andvalidate final customization for Req/Cat 103 P34 Produce custom Req/Catprograms 103 P341 276 Validate and code bridge change requests (SAP andReq/Cat) P4 EDUCATION AND TRAINING 102 P41 Develop customer educationand training strategy 102 P411 Validate customer education & trainingobjectives 102 P412 190 Define the training requirements and approach102 P413 Confirm the education & training strategy 102 P42 Define systemmanagement processes 102 P421 Define SAP correction and transportprocess 102 P422 Define and agree on service level agreement SLA 102P423 Define and administer SAP release control process 102 P424 DefineReq/Cat transport process 102 P425 Define and administer version controlprocess 103 P43 192 Define user documentation and training requirements103 P431 Define customer user audiences and requirements 103 P432Confirm user documentation requirements and standards 103 P433 Conductdetailed end-user task analysis 103 P434 Assess user skills and trainingneeds 103 P435 Validate end-user courses and content 103 P436 Identifyusers and course attendees 103 P437 Define and notify training attendees103 P44 Develop user training documentation 103 P441 Produce customerspecific end-user documentation 103 P442 Confirm training evaluationmaterials/approach with customer 103 P443 194 Setup training systemenvironment 103 P444 Validate training logistics 103 P445 198 Conductpilot training with super users 103 P446 196 Arrange documentation andtraining material production 103 P45 Internal (Enterprise, serviceprovider) training requirements 103 P451 Identify and organizeappropriate internal training 104 P46 Conduct end-user training 104 P461Conduct train-the-trainer sessions 104 P462 214, Perform training 230104 P463 212 Conduct new buyer training P5 IMAGE 103 P51 Conduct imagefunctional detailed fit gap analysis 103 P511 Define the imagefunctional detailed fit 103 P512 Resolve image functional gaps 103 P52Configure image offering 103 P521 Refine and validate final imageconfiguration 103 P522 Confirm and refine image initial settings P6 I/T103 P61 Establish customer network/computing infrastructure 103 P611Confirm component delivery 103 P612 Establish network/computinghardware/software architecture infrastructure 103 P613 Readynetwork/computing environment 103 P62 Establish EDI infrastructure 103P621 Establish EDI infrastructure 103 P622 conduct trading partnertesting (IT) 102 P623 Confirm EDI strategy 102 P6231 Setup image systemenvironments 103 P6232 Establish cutover checklist and performpre-cutover activities for image production environment 104 P6233Validate image production support for system management 103 P63 Developreporting infrastructure 103 P631 Develop reporting infrastructure(LIS/EIS) 103 P632 Develop DataMart extracts 103 P633 232 Developadditional reports (customer/operations) 102 P64 Perform bridgearchitecture assessment 102 P641 Perform bridge architecture integrationpoint interfaces work session 102 P642 158 Define bridge architectureproject objectives document 102 P65 Validate bridge, EDI, vendorreporting requirements 102 P651 270 Develop and manage bridgearchitecture implementation work plan 102 P652 Analyze EDI requirements102 P653 Determine EDI communication environment 102 P654 Analyze vendormaster data load 102 P655 Analyze operational reporting requirements 102P656 Analyze customer requirements for DataMart implementation 102 P657Schedule and conduct weekly interlock meeting 102 P658 Vendor leadclient analysis 102 P66 Set up development/integration environment 102P661 Set up SAP development/integration environment 102 P662 Set upReq/Cat system environments 103 P67 Set up consolidation/testenvironment 103 P671 Set up SAP consolidation/test environment 104 P68218 Set up production environment 104 P681 Convert vendor master intoproduction environment 104 P682 Determine EDI tasks for productionenvironment set up 104 P683 Execute SAP cutover checklist 104 P684 Setup SAP production environment 104 P685 Establish SAP batch schedule 104P686 Set up trading partners in production environment 104 P687 Vendorlead client deployment 103 P688 Establish cutover checklist and performpre-cutover activities for SAP production environment 103 P689 Establishcutover checklist and perform pre-cutover activities for e-Req/Catproduction environment 105 P69 Refine/execute production support forsystem management 105 P691 234 Perform on-going support activities forReq/Cat 105 P692 Post deployment reporting support 105 P693 Develop newbridges and application extensions post go live 105 P694 236 Support newEDI transactions post go live 105 P695 Execute system managementsecurity support procedures 105 P696 Execute data management supportprocedures 105 P697 236 Execute EDI support procedures 105 P698 Executesystem management operational support desk procedures 105 P699 Executesystem management batch support desk procedures 105 P69A Execute systemmanagement SAPBI support procedures 105 P69B Execute system managementmaster data support procedures 105 P69C Execute production support forsystem management 103 P6A Establish vendor master environment 103 P6A1Establish vendor master 103 P6A2 Confirm vendor master 103 P6A3 ALEconfiguration for VLC 103 P6B Establish bridge architectureinfrastructure environment 103 P6B1 272 Develop detail architecturerequirements definition 102 P6C 274 Validate system infrastructurerequirements 102 P6C1 280 Analyze current network/computinginfrastructure 102 P6C2 Determine network/computing requirements forproject 102 P6C3 Confirm and begin network/computing componentacquisition 102 P6C4 Order and delivery of infrastructure components P7MARKETING 100 P71 Participate in marketing procurement consultingengagement 100 P711 170 Qualify potential client 100 P712 Qualifypotential client e-Req/Cat 100 P713 Develop assessment statement of work(SOW) e-Req/Cat 100 P714 Develop assessment statement of work (SOW) P8PROCESS 102 P81 156 Customer process introduction 102 P811 Conductcustomer introduction to Golden procurement and A/P processes 102 P82Process reviews with customer - procurement and A/P 102 P821 344 Reviewprocurement processes with customer 102 P822 342 Review A/P processeswith customer 102 P83 Assess customer impact on internal Enterpriseworkload 102 P831 Identify current and potential supplier catalogs forcustomer 102 P832 340 Perform assessment of customer purchasing business103 P84 Process alignment customer/Golden 103 P841 Determine GAPsbetween customer and golden processes 103 P842 Perform process GAPresolution 103 P85 BMP process and procedures management 103 P851 Codesand procedures 103 P852 348 Update and review process management &procedures manual 103 P86 Supplier readiness 103 P861 210 Generalsupplier introduction 103 P862 Manage trading partner-EDI suppliers 103P863 346 Establish ASAP suppliers for customer (ASAP = a SAP suppliernot requiring a buyer) 103 P864 Manage customer supplier outlineagreements 103 P865 Customer freight procedures 104 P866 Supplier memomailing P9 PROJECT MANAGEMENT 102 P91 180 Initiate project planning 102P911 160 Confirm project scope and implementation strategy 102 P912Confirm project organization and assign resources to roles 102 P913Prepare and validate project plan and procedures 102 P914 Establishproject team working environment 102 P915 Orient project team 102 P92150 Confirm and refine project management standards and procedures 102P921 Confirm and refine issue management plan 102 P922 Confirm andrefine project documentation 102 P923 152 Confirm and refine qualityassurance standards 102 P924 Create team building plan 102 P93 Confirmimplementation strategies 102 P931 Confirm system Configurationstandards 103 P9311 Customize image offering 103 P9312 Validate andcustomize image core application change request 103 P93121 Refine andvalidate final customization for image 102 P932 Confirm CR/PTR process102 P933 Confirm testing strategy 102 P934 Confirm production support &operations strategy 102 P935 Confirm SAP production system managementstrategy 102 P936 Confirm e-Req/Cat production system managementstrategy 102 P937 282 Confirm network/computing strategy 102 P938Confirm vendor conversion strategy 102 P94 162 Prepare project team 102P941 Conduct kick-off meeting 102 P942 Conduct project team standardsmeeting 102 P943 Conduct project team training 102 P95 352 Defineproduction support plans 102 P951 Define system management SAP resourcerequirements 102 P952 Define system management e-Req/Cat resourcerequirements 102 P953 Define production support accounts payable plan102 P954 Define production support CSC plan 102 P955 Define productionsupport general procurement plan 102 P956 Confirm SAP systemauthorizations for project team 102 P957 Confirm Req/Cat access controllist (ACL) 102 P958 Define system management image resource requirements102 P96 Initial quality assurance review 102 P961 Initial QA review 103P97 Review project status and refine project & 104 plan 103, P971Conduct project team status & 104 meetings 103 P972 Conduct steeringcommittee meetings & 104 101 P98 Obtain customer approval 102 P981 Wonbid analysis/transition to implementation team 102 P982 Won bidanalysis/transition to implementation team e-Req/Cat 101 P983 Conductlost bid analysis 101 P984 Conduct lost bid analysis e-Req/cat 104 P99Validate production support 104 P991 Validate SAP production support forsystem management 104 P992 Validate production support for accountspayable 104 P993 Validate production support for CSC 104 P994 Validateproduction support for general procurement 104 P995 Validate Req/Catproduction support for system management 105 P996 Validate education &training production support activities 104 P9A Perform go live projectoffice activities 104 P9A1 Ensure go live check lists activities 104P9A2 Go/no-go decision for go live 103 P9B Interim quality assurancereviews & 104 103 P9B1 Interim QA reviews & 104 105 P9C 244Post-implementation quality assurance review 105 P9C1Post-implementation QA review 105 P9D Production support review 105 P9D1Confirm production environment PA REQ/CAT 102 PA1 Identify customerresponsibilities for Req/Cat 102 PA11 Identify country/globaladministrators & neg. con person 102 PA12 Perform country administratoreducation 103 PA2 Prepare and load Req/Cat catalog data 103 PA21 PerformReq/Cat catalogue tasks 104 PA3 Req/Cat production readiness 104 PA31Confirm Req/Cat for production environment 104 PA32 Set up Req/Cattables in production 104 PA33 Prepare Req/Cat production copy 104 PA34Execute Req/Cat go live checklist PB SAP 103 PB1 254 Conduct SAPfunctional detailed fit gap analysis 103 PB11 250 Confirm SAPorganizational hierarchy 103 PB12 Define the SAP functional detailed fit103 PB13 Resolve SAP functional gaps 103 PB2 Produce custom SAP programs103 PB21 Develop and validate SAP custom programs 103 PB3 252 ConfigureSAP offering 103 PB31 Confirm and refine implementation guide 103 PB32Confirm and refine SAP initial settings and organizational structure 103PB33 Confirm and refine SAP end user authorization profiles 103 PB34Refine and validate final SAP configuration 103 PB4 Customize SAPoffering 103 PB41 Validate and customize SAP core application changerequest 103 PB42 Refine and validate final customization for SAP PCTESTING 103 PC1 256, Perform preparation activities for 260, testing(both Req/Cat and SAP) 322 103 PC11 Confirm and refine test casetemplates 103 PC12 258, Build comprehensive test plan 326 103 PC13Develop test environment plan 103 PC14 Create test case specifications103 PC15 Build/reuse test cases 103 PC16 Determine testing tools 103PC17 Review and validate comprehensive test plan 103 PC2 216 Performcomprehensive testing 103 PC21 Perform unit test 103 PC22 262 Performcomponent test 103 PC23 264, Perform integration test 328 103 PC24Administer network/computing performance monitoring 103 PC25 266,Perform system test 330 103 PC26 220 Perform user acceptance test 103PC27 Perform other required testing 103 PC271 Support comprehensiveimage testing 103 PC28 Support comprehensive e-Req/Cat testing 103 PC29Support comprehensive SAP testing 103 PC2A support comprehensive imagetesting PD TRANSITION MANAGEMENT 101 PD1 172 Introduce transitionmanagement (assessment) 101 PD11 172 Develop initial assessment ofclient 101 PD12 Provide transition management workshop presentation 102PD2 154 Model transition management (project preparation) 102 PD21Provide transition management strategy 102 PD22 Evaluate cultural impactof solution 102 PD23 300 Develop/confirm transition management plan 102PD3 Develop communication plan (project preparation) 102 PD31 304Build/confirm campaign plan 102 PD32 302 Update communications strategy102 PD33 Deliver announcement/kickoff communication 103 PD4 Initializetransition management (design and development) 103 PD41 Createincentive/reward program 103 PD42 Assess supplier impacts related totransition management 103 PD43 Assess Enterprise support impacts relatedto transition management 103 PD44 Design detail go livematerial/activities 103 PD45 308 Create policy changes 103 PD46Identify/plan for security 103 PD47 Detail process transition plan 103PD48 306 Detail human resources plan 103 PD49 Detail employee relationsplan 104 PD5 Ensure transition management activities (deploy) 104 PD51350 Ensure new process management system in place 104 PD52 222 Performclient readiness assessment 104 PD53 Perform transition management golive activities 104 PD54 240 Manage human resources activities 105 PD6Communication (support) 105 PD61 Thanks to users/suppliers 105 PD7Validate transition management (support) 105 PD71 Monitor human resourceissues 105 PD72 Assess effectiveness of transition management program105 PD8 Perform post implementation survey (support) 105 PD81 242Administer post go live survey 105 PD82 Present and act upon surveyfindings PE NOT CATEGORIZED 104 PE1 200 Perform go live processactivities 104 PE11 Allocate buyer codes to commodities 104 PE12 Enterblanket orders ... PE2 Table template document PE21 Table templatedocument

Project Assessment 101 Referring to FIG. 3 in connection with FIG. 2,project assessment phase 101 follows pre-sales phase 100, during whichmarketing makes its initial contact with the prospective client, orcustomer.

After initial contact from marketing 118, the main thrust of AssessmentProject 101 is to provide an integrated, cross-functional customersolution to the client. An assessment team is led by the Business Office120, but requires input and participation from the project leaders ofArchitecture 122, Transformation Management 136, Business Process 112,EDI 114, and Application Development 116.

Assessment 101 begins with a complete review of the client's currentgeneral procurement and accounts payable processes. This includesdebriefing the initial marketing team 118, instructing the projectleaders 126, and accumulating all other relevant data available aboutthe client's processes, tools, and organizational structures.

The Assessment Team then defines an integrated customer solution thatcovers technical, educational, and Human Resource issues.

The delivery of the Workshop is intended to present an overview of thecustomer solution, initiate discussions on process analysis andstrategic implementation, and confirmation of the solution fit. Specificgoals of a workshop phase within assessment stage 101 include thefollowing:

(1) Prepare and deliver a presentation to the customer defining theservice offering, including any essential documentation on the offering,and a demonstration of the end-user tool(s), as applicable.

(2) Collect area specific information and customer requirements onnetwork process sourcing, procurement, accounts payable, and finance;and EDI, I/T, and transition management.

(3) Identify high level gaps in each such area.

(4) Identify additional high level requirements for new process support,and for conversion requirements, including requirements for commoditystructure, account structure, vendor, and contracts.

(5) Identify interface requirements, including requirements for HR, costcenter, catalogs, ledger, information warehouse.

(6) Validate accounting for project, appropriation, contract, job, taxreporting, currency, and check reconciliation.

(7) Identify requirements for network, EDI, testing, and applicationdevelopment including new reports, new interfaces, and new features.

(8) Assemble a high-level gap analysis.

(9) Create a high-level Customer Scope Document.

(10) Confirm the recommended solution.

At the completion of the workshop phase, the assessment team 106convenes to develop and cost the final customer solution and proposal.At this time, the members of assessment team 106 assemble, understand,and validate the collected data; review standard proposal options withassumptions and identify items that apply to this client; create a draftof the proposal including scope, risk, schedule, and resources; reviewthe draft with team and other project members to obtain sizing andcosting information for each area; compile costing information to add tothe proposal; and perform QA review of the system integration,application development, managed operations (including service deliverycenter (SDC), application IT, and Process Operations) proposals, and ofthe overall proposal.

The resulting proposal is delivered or presented to the client. FinalAssessment activities include follow up query responses and, should theproposal be declined, a loss analysis. This loss analysis feeds backinto assessment process 101 to improve its overall effectiveness andefficiency.

Referring to Table 4, summary tasks pertaining to assessment stage 101are listed, together with included detail tasks. For each task, atemplate 440 or 520 is maintained in data base 70, and accessed by team108 members and others through summary view 400 to track progress(including viewing, updating, sharing, and approving) during thisassessment stage 101.

Project Preperation 102

Referring further to FIG. 3, project preparation stage 102 sets up theproject, initializes detail planning, and models the plan for making thetransition from the client's legacy system and process to the new systemand process (or, offering).

A critical element of this stage is to ensure resources are assigned totransition management 136, both from the project implementation team 126as well as from the client. During this stage the transition activitiesrequired for a smooth migration from the old client process and systemto the new service offering are modeled. The result is a detailedtransition management plan that is specifically designed for the client.Stage 102 tasks and deliverables include the following:

(1) Perform analysis on the client HR environment, includingorganization structure and relationships, labor relations, management,administration, and end user roles and responsibilities, and the generalHR environment.

(2) Develop and approve the detailed transition management andcommunication plan.

(3) Update the client specific transition management strategy.

(4) Define the quality assurance (QA) process required to assure that aproject conforms to documented standards and meets documentedrequirements. The purpose of this task is to confirm the qualityassurance standards between Enterprise and the client, and identifiesthe tasks that are to be audited by the Enterprise Technical Center.

The QA review is a beneficial process for the project as it timelyrecognizes potential risk areas and reduces the possibility of projectdelays while achieving faster implementation, attaining low cost andincreasing the customer's level of confidence. Deliverables of the QAreview task include the following:

(1) Confirm and refine quality assurance standards with the customer.

(2) Confirm that technical requirements can be met.

(3) Confirm that business and financial measurements can be met.

(4) Confirm that the proposal is complete and the required processeshave been followed.

(5) Establish QA schedule for the project.

Integration of all critical Enterprise and client team members providesthe glue to assure a smooth project. By completing the detailed taskswithin project preparation stage 102, the recommended implementationstandards, procedures and strategies for the project are shared with thetechnical and business functional members of the project team as well aswith the customer. All team members have input in this process, andunderstand the basic procedures, once they have been agreed to. Theseprocedures, documented in summary and detail task templates listed inTable 4, include the following:

Configuration Standards

CR/PTR Process

Testing Strategy

Production Support and Operations Strategy

SAP System Management Strategy

Req/Cat System Management Strategy

Network Computing Strategy

Vendor Conversion Strategy

Project Design and Development 103

Referring further to FIGS. 3, project design and development phase 103provides and documents in a database of templates referred to as aPlaybook, the business controls, transformation management, and SAP andReq/Cat customization required for an integrated approach to a completecustomer solution.

During this stage 103, business controls 132 provides a comprehensiveprocess that identifies key control points and establishes detailedprocedures to assure a quality installation. The deliverables includedocumentation, separation of duties, sensitive programs, logical accesscontrol, logging (audit trail), change control for tables, changecontrol for programs, system testing, input controls, processingcontrols, error handling controls, output controls, balancing andreconciliation, vital records and disaster recovery, records management,reports, local area network (LAN), and country specifics, as describedbelow:

(1) Documentation: an assessment of the quality and completeness ofexisting program documentation and a determination of the degree towhich programs could be efficiently reconstructed if they weredestroyed.

(2) Separation of duties: the duties of the programmer, computeroperations, and user groups are reviewed to ensure that separation ofduties problems do not exist.

No one individual can control activities within a process (or any eventin a string of events) in a way that permits errors of omission, orcommission of fraud, theft, etc., to go undetected.

(3) Sensitive programs: controls must be in place to preventunauthorized modification and/or use of the application.

(4) Logical access control: while programs are generally controlled by asite procedure, application data has a formal access control mechanism.

(5) Logging (audit trail): a logging mechanism is established to ensurethe audit trail is correct.

(6) Change control (tables): a change control system is put in place toevaluate, justify and control changes to tables.

(7) Change control (programs): a change control system is put in placeto evaluate, justify and control changes to programs.

(8) System Testing: system testing procedures are effectively plannedand carried out to ensure that controls are successfully tested anddocumented.

(9) Input controls: to insure accuracy and completeness of informationentering an application.

(10) Processing controls: controls are applied for entry of data intothe computer application system that ensure accuracy and completeness ofdata during computer processing.

(11) Error handling controls: controls for error handling andreprocessing of transactions.

(12) Output controls: output controls ensure the integrity of the outputdata from conclusion of computer processing to delivery to the user.

(13) Balancing and reconciliation: verifies that procedures to reconcileoutput to input are effective.

(14) Vital records and disaster recovery: disaster recovery is designedto provide for the continuity or rapid system restoration of a businessprocess immediately following a natural or man-made emergency ordisaster.

(15) Records management: verify that information is managed with soundbusiness practices and controls.

(16) Reports: verify that reports are distributed properly.

(17) Local Area Network (LAN): Refer to ITCS 201, “Security Standardsfor Local Area Networks and Distributed Computing.”

(18) Country specifics: verifies that any questions particular to thisspecific country are completed.

Req/Cat is a requisition and catalog product designed, developed, andmaintained by Enterprise for use in systems such as those developed inthis stage 103.

SAP is an financial and accounting package which an enterprise orcompany may license for its own use and for its customers. SAPconfigurators that customize package programs to fit the needs of theclient are provided for use during design and development stage 103. Allother installations of SAP are “off the shelf”, with the client changingits internal structures to fit SAP requirements.

Transition management is the most overlooked part of any implementationprocess. It is critical to address the corporate culture and personalityat the earliest contact. Strategic and tactical plans may then bedeveloped that guide the implementation through “Go Live” and for anagreed period thereafter. The purpose of transition management steps ofthe design and development stage 103 is to provide guidance to thedevelopment team members as they work with the client to institutepolicy changes that might be introduced as part of the implementation ofthe new process and system. Necessary changes to the legacy system areidentified and a plan developed to announce and introduce changes inpolicy. Policy change includes key business rules that are part of themanagement system for purchasing and procurement. They may be associatedwith approval levels or procedural changes in the new system. The targetis not the day to day operation but management decision and supportsystems that might be affected. The areas addressed include:

Measurements (old and new)

Management system

Approval levels

Supplier contacts and contracts

Reward systems

Incentive Plans

Security

Employee and user changes

All of these areas require strategic and tactical planning that includesthe following steps:

(1) Identify the current (legacy) system or process and compare it tothe new process or system to be implemented to identify gaps.

(2) Develop specific recommendations for gaps between the legacy and thenew system or process, identifying the level of sensitivity and whetheror not action is required as part of the transition.

(3) Determine the announcement and transition (or, cut over) date foreach action identified.

(4) Design a communications plan to build the message and media forcommunicating the changes to affected parties.

(5) Design a process transition plan to ensure the elements of changeare integrated into the overall plan for the process.

(6) Determine how the policies must be modified according to newstandards and procedures

(7) Determine what new policies and procedures will be implemented aspart of the process and system.

Finally, integration of the above design and development stage 103process steps along with the technical teams involved allow the deliveryof a cross-functional solution under one unified and managed plan.

Project Deployment 104

Referring again to FIG. 3, project deployment phase 104 uses thePlaybook to improve deployment of (1) quality, or application systemscontrol and auditability (ASCA), (2) transition management, and (3)integrated project management systems and procedures.

1. Quality (ASCA)

A business controls team provides dedicated resources throughout thelife cycle of the project. During the project development stage 103,this team has planned and executed an ASCA self-assessment that hascovered an extensive list of technical, business, financial, and clientissues. In this deployment stage 104, its members are responsible formanaging an independent audit that will cover the same areas. Theindependent auditors then issue an acceptance position that is requiredbefore the client can “Go Live” with the new system and process.Deployment stage 104 activities include:

(1) Create the project plan for ASCA Review preparation activities.

(2) Determine which Enterprise organization will conduct the ASCA andbusiness controls review.

(3) Prepare all ASCA documentation required for the review.

(4) Prepare all sub-process overviews and descriptions of process flow.

(5) Ensure the test plan includes those elements of the ASCA checksrequired to ensure business controls, separation of duties, andauthorization matrices, data integrity and security.

(6) Create, update and complete all required documents of understanding(DOU's) & service level agreements (SLA's).

(7) Ensure the separation of duties matrix (SOD) is current at time offinal review.

(8) Review all testing and obtain test approvals.

(9) Ensure all approvals have been obtained and signed approval formsavailable for ASCA Review. These include approvals for processownership, ASCA requirements, self-assessment and system cutover.

2. Integrated Project Management

During this deployment stage 104, project manager 126 has the task tovalidate and confirm that all checklists and status are acceptable priorto Go-live. This includes the readiness of all aspects of the project,and once satisfied, a review is conducted and the customer's formalsign-off for Go-live is obtained. Status transition management andclient readiness assessment and confirmation activities includeverification that:

(1) No critical open issues exist in any area.

(2) All relevant aspects of readiness have been included in the statuscheck.

(3) Network and computing performance testing is complete.

(4) System test is complete.

(5) User acceptance test is complete.

(6) System management production environment Go-live checklist iscomplete.

(7) Any needed CR's and PTR's have been generated.

(8) Production support is in place.

(9) Supplier readiness is reviewed and accepted.

(10) Service provider readiness is confirmed.

(11) Enterprise GP readiness is confirmed.

(12) Review of the compiled check information is completed.

(13) Customer sign-off on the Go-Live decision is obtained.

3. Transition Management

A transition management team prepares for the deployment, or “Go Live”of the client solution. During this deployment stage 104 in the project,virtually all technical problems are resolved and systems configured.The client is now ready to deploy and the human factors must beaggressively managed to assure a smooth transition from the legacysystems to the improved client solution. Transition managementactivities within deployment stage 104 ensure that organization,measurements, management, support, and labor relations functions aredeveloped, explained, reviewed, understood, in place or on schedule, asappropriate.

(1) Organization: organizational changes for Go-Live, updatedcommunications plans, feedback mechanism for persons displaced bychanges in organization, and the new organization.

(2) Measurements: changes in measurement system, plan to cut over to thenew measurements, and communications explaining the new measurements,including how they are derived, how they are used and their importanceto the business.

(3) Management: changes in management or management responsibilities,communications explaining the changes in management structure, and whyit is important to the clients' organization, the management chain andpath for escalation of issues, normal business reports and their use.

(4) Support: support structure for both client and technical support.

(5) Labor Relations: activities associated with the loss of a job role,plan to notify the affected people, communication plan for providinginformation to remaining employees on the reasons for the changes andfor fostering support for the new process.

Integration of the cross-functional teams to accomplish the deploymentof the customer solution is facilitated by use of the system and database structure of the preferred embodiment of the invention.

Ongoing Project Support 105

Referring further to FIG. 3, project support stage 105 enables projectteams, all of which have continuing responsibilities with the clientafter “Go Live”, to provide the required ongoing support. As with allother stages, integration of the teams through the use of the systemsand methods provided by the invention, including transition managementsystems and methods, is greatly facilitated. It is a characteristic ofthe preferred embodiment that each of these areas has specificpredetermined plans, actions and responsibilities, and these are auditedand tracked through a GP/AP development and deployment system.

During support stage 105, transition management 136 delivers an approveddetailed questionnaire with quality questions in a logical format thatallows end-users to express their opinion and provide information thatmeets the survey objective. Support stage 105 includes a plan forcommunicating the survey results to the participants and taking actionin response to the survey results. This stage also incorporates acontinuing education plan for training new employees as well ascontinually updating the material so that reflects the latest version ofthe application.

The survey in stage 105 is structured to determine the end users'perception of the new system, system ease of use, response time fromboth the system and CSC (Customer Service Center), and customerknowledge level of processes and product. Results of the survey arecompiled and presented to the client and Enterprise Management Teamsalong with action plans, time tables, expected results for approval, andimplementation. A Lessons Learned document is reviewed with the projectteam and appropriate adjustments made for future engagements.

Project Manager 126 provides a quality function task after “Go Live”.This task aims at checking the implementation of the EPS Offering todetermine if anything needs special attention or focus. It is also theformal sign-off on the final delivery of the implementation by thecustomer. Its deliverables include:

(1) Customer accepts delivery of the EPS general procurement offeringimplementation and signs off.

(2) Action list on issues and CR/PTR's, if applicable.

(3) Formal transition of operational responsibility to operations 98 andsupport management 96.

(4) Preliminary business benefits evaluation.

The Req/Cat and SAP technical teams 128, 138 provide ongoing reviews andimprovements to the client's process through the CR and PTR processes.These are formalized, documented processes with management controls toattain cost, schedule, and customer objectives.

As part of the new business process, support center 94 is established toprovide long term assistance in any area of the application solution.This includes communication of feedback, real time applicationassistance, and special requests for problems concerning data.

It is the planned integration of these multi-functional teams thatprovides an innovative solution to the customer.

Representative Implementation of Ongoing Support Stage 105

Referring to FIG. 3E, a series of steps illustrating an exemplaryselection of tasks in ongoing support stage 105 will be described.

While steps 230-244 represent a selection of key steps in stage 104,other summary and detail tasks designated in Table 4 as pertaining tostage 104 are typically included in the initial set of templates forthis customer, and are also used as they are determined to beapplicable. Some field entries are dynamic and changeable during thecourse of ongoing support stage 105. The templates are also editable fora particular project, and do not necessarily continue during use toconform to the original format.

In step 230, ongoing training, similar to that of step 214, is provided.Education material is supplied and maintained to the latest version ofReq/Cat to the client, this is distributed using distance learningtechniques.

In step 232, the data warehouse team accesses detail task template P633in the course of developing additional reports. Task P633 is originallyexecuted in stage 103, and is also applicable to on-going support stage105. This task describes the steps necessary to complete in stage 103the development required to support the Operational Reporting needsduring on-going support stage 105. Template P633, Table 27, provides,either directly or by way of links to other documents, instructions,flow charts, sample questionnaires, report models and checklists forguiding, coordinating and documenting the work of the data warehouseteam.

TABLE 27 DETAIL TASK: DEVELOP ADDITIONAL REPORTS CREATION STATUSCategory: I/T Team: Data warehouse Offering type: Req/Cat, SAP,Req/Cat&SAP Stage: 3. Design & Development IMPORTANCE BUTTONS Education:No Certification: Yes Auditable Yes Critical path Yes IMPLEMENTATIONExecuted by: Service provider Performed by: Customer, reporting analystPriority: High Work effort: 15 days Sequence: 3 months prior DETAIL TASKDETAILS Description: This task describes the steps necessary to completedevelopment required to support the Operational Reporting needs. Thistask Will use the CR's identified in the Analyze Operational ReportingRequirements detail task from the Project Preparation stage. Detailrequirements will be realized and resolutions will be researched,defined, documented and agreed on by the customer, operations team andthe Reporting implementation team members. Prerequisites: Gaps must havebeen documented on a CR form(s) and initiated in the Analyze OperationalReporting Requirements detail task in the Project Preparation stage Tasksteps: 1. Perform Required Development - Review the CR form, update theform with additional development requirements (it required). For theCR's assigned to the Reporting team, complete necessary actions fordevelopment of these: Develop Reports Update Reporting Tree UpdateReport List Document 2. Interlock with AD Team - For the CR's assignedto the SAP AD team review requirements with team and discuss developmentmethods. 3. Interlock with Image Team - For the CR's assigned to theImage AD team, review requirements with team and discuss developmentmethods. 4. Unit Test - All reports developed via CR must be unit testedprior to transporting the code to the Test environment. Unit testReporting team development Document test results Obtain customer signoff on unit test Participate in SAP AD team development Reviewdocumented test results Sign off on successful testing Participate inImage AD team development Review documented test result Sign off onsuccessful testing 5. Submit Transport - Once unit testing has beencompleted and signed off, the code must be moved into the Test systemfor formal System, User and Integration testing responsible for owntransports and coordinate any AD involvement). Ensure all transportsexist Submit transport to target system Verify transport successful 6.Support Testing Process - It is necessary to be available to provideexplanations of development or to answer questions regarding anysubsequent changes identified via a problem log (PTR). Obtain sign offfrom Test team Ensure transport to Production system has been initiated7. Update Reporting Document - Update all relevant documents. Update thedocument with the changes and additions in fields, values, reports, etc.(i.e. BPMGP) Update the standard list/golden list of reports 8. Traincustomer - If training is required for the operations team on theadditional reporting specifications the following should be considered.Update training material Schedule training with Operations Performnecessary training 9. Update Reporting Project Plan - The Reporting Teamproject plan should be updated accordingly with new development work,dates and detail required to complete this task. Deliverables:Development Documentation Supporting New/Changes to Reporting codeUpdated CR Form Unit Test Results Transport Request to Test System TestTeam Sign Off Updated Report Instruction Document (if required)Reporting Team Project Plan Methodology attachments: The followingdocument links contain the attachments necessary to complete this task:Sample Development Documentation supporting New/Changes to ReportingCode => Report Instruction Document => Sample DataMart Decision PointMatrix => PROJECT REFERENCE AREA Comments & Dialog: Step Checklist: 1.Perform required development - update CR form. 2. Interlock with SAP ADteam - describe reporting requirements. 3. Unit test - document testresults. 4. Submit transport to test system. 5. Support testingprocess - obtain sign off on successful test. 6. Update reportinstruction document. 7. Train operations team. 8. Develop reportingproject plan.

In step 234, the Req/Cat team accesses detail task template P691, Table28, in the course of providing ongoing Req/Cat support. After theReq/Cat system has Gone Live, the system is monitored any productionproblems that occurred solved. Template P691 provides, either directlyor by way of links to other documents, instructions, flow charts, samplequestionnaires, report models and checklists for guiding, coordinatingand documenting the work of the Req/Cat team through the task.

TABLE 28 DETAIL TASK: PERFORM ON-GOING SUPPORT ACTIVITIES FOR REQ/CATCREATION STATUS Category: Req/Cat Team: Req/Cat Offering type: Req/Cat,SAP, Req/Cat&SAP Stage: 5. Ongoing support IMPORTANCE BUTTONS Education:Yes Certification: No Auditable: Yes Critical path: No IMPLEMENTATIONTask order: 1 Executed by: Service provider Performed by: Req/Cat AdminPriority: Medium Sequence: One day after DETAIL TASK DETAILSDescription: After the Req/Cat system has Gone Live, you will need tohave people allocated to monitor the System and solve any productionproblems that occurred. Generally, the Global and Country administratorswill be responsible for the daily monitoring of the Req/Cat tableinformation and the feed of data through the Req/Cat tables.Prerequisites: The Req/Cat system has Gone Live The Post ProductionSupport structure/process has been implemented Task steps: Daily, theCountry and Global administrators will need to monitor the Req/CatProduction system to identify errors, analyze the cause, and determinethe resolution path. To monitor the system, you will need to look in thesystems logs and the bridge ID's e-mail. There will be times when the CAor GA can fix the problems themselves and other times when a CR or PTRwill need to be raised. Refer to the attachment Req/Cat ProductionSupport Procedures for a complete description of the ongoing supportprocedures for Req/cat. Daily, the CA and GA will need to maintain thecatalogs, HR feeds, cost centers fields, and country table information.Generally, the most errors will occur with the HR and Cost Center feeds.In additional the table monitoring tasks, the support people will needto look at how the process are working and identify and concerns orsuggestions for improvements. The CA and GA will also need to workclosely with the Customer Service Center (Help Desk) to answer questionsthey may have to serve as the second point of contact for issues orquestions that are raised by callers. Obviously, the SCS/Help desk willattempt to answer all questions first, but there will be problems orquestions where the will need assistance for resolution. For the firstfew weeks after production cut over, there should be daily support teammeeting to identify major problems, concerns, etc. The CA and GA shouldattends these meetings and actively participate in the discussions andresolution process. Any open issues or unresolved problems should beaddressed to the Production Support Leader and escalated if they are notsolved within a reasonable amount of time. Deliverables A Req/Catproduction support structure with defined procedures and roles.Methodology attachments: Req/Cat Production Support Frocedures ->

In step 236, the EDI team accesses detail task templates P694 (Table 29)and P697 (Table 30) in the course of supporting EDI transactions post golive. These tasks cover data management, help desk support procedures,report generation, and security. Templates P694 and P697 provide, eitherdirectly or by way of links to other documents, instructions, flowcharts, sample questionnaires, report models and checklists for guiding,coordinating and documenting the work of the EDI team through the stepsof these tasks.

TABLE 29 DETAIL TASK: SUPPORT NEW EDI TRANSACTIONS POST GO LIVE CREATIONSTATUS Category: I/T Team: EDI Offering type: Req/Cat, SAP, Req/Cat&SAPStage: 5. Support IMPORTANCE BUTTONS Education: Yes Certification: YesAuditable: Yes Critical path: No IMPLEMENTATION Executed by: Serviceprovider Performed by: EDI specialist Priority: Medium Work effort: 30days Sequence: One month after DETAIL TASK DETAILS Description: Thecustomer may choose to add additional transactions once the selectedservice offering has been implemented. The following EDI transactionsare standard and are most often added after the customer goes live tomeet additional requirements: 840 - RFQ 843 - Response to 840 832 -Price/Sales Catalog 856 - Ship Notice/Manifest For non-standardtransactions the same steps should be followed, however a CR will needto be created, bid and approved through the CR Process Flow before theadditional work can be done. Prerequisites: Customer must be using EDIin a production environment for the selected service offering. Tasksteps: 1. Confirm customers current EDI Infrastructure - Review theproject documentation that specifies EDI infrastructure for customer 2.Define New Requirements - Meet with the customer to define newrequirements and transaction needed for the Production environment,compare requirements to Golden IDOC for transaction Analyze customerrequirements Transactions IDOC'S Data Fields ˜Required ˜Optional 3.Create Trading Partner Transaction Map - For each ANSI X.12 transactionselected, independent of how many trading partners exist 4. Interlockwith Req/Cat and SAP units of measure - To ensure integrity of order ofdata ANSI standards 5. Interlock with Trading Partners - Communicate allcustomer specific requirements for new transaction to trading partnersDefine Media Letter Meeting/Forum Web Page Convey business strategy fornew transaction 6. Identify Trading Partner Issues - All issues from theinterlock with trading partners must be documented and presented to thecustomer for a decision 7. Unit Test - Once system communication hasbeen established follow the test check list to complete the unit testVerify Mapping Test JCL Add to Job Stream Document Test Results 8. MoveTo Production Environment - Once all testing has been completedsuccessfully and customer sign off has been obtained schedule move intoProduction, follow EDI Go Live Check List Deliverables: New Requirementsfor EDI Transactions documented Communication to Trading Partnersregarding new transaction requirements Trading Partner Transaction MapUnit Test Results New Transaction(s) Moved to Production SystemsMethodology attachments: The following document links include allnecessary attachments to complete this task: Web Page Link EDI ChecklistEDI TP Package PROJECT REFERENCE AREA Comments & Dialog: Step CompletionTracking Checklist: 1. Confirm customers current EDI infrastructure.2. Define new requirements. 3. Create trading partner transaction map.4. Interlock with Req/Cat and SAP units of measure. 5. Interlock withtrading partners. 6. Identify trading partner issues. 7. Unit test.

TABLE 30 DETAIL TASK: EXECUTE EDI SUPPORT PROCEDURES CREATION STATUSCategory: I/T Team: System Management Offering type: Req/Cat, SAP,Req/Cat&SAF Stage: 5. Support IMPORTANCE BUTTONS Education: YesCertification: Yes Auditable: Yes Critical path: No IMPLEMENTATIONExecuted by: Service provider Performed by: EDI specialist Priority:Medium Sequence: Ongoing support DETAIL TASK DETAILS Description: Thistask provides the steps, attachments and desk procedures required tosupport the EDI process in a Production environment. Task steps: 1.Maintain and Follow EDI Setup Procedures (GP): Inbound Outbound Test CPSNorth Production CPS Test 2. Maintain and Follow Web EDI Setup:Analysis: Deliverables: EDI Support Maintenance Desk ProceduresMethodology attachments: The following doclink will provide theattachments necessary to complete this task => EDI Setup Procedures:Inbound Outbound Test CPS North Production CPS Test Web EDI setup:PROJECT REFERENCE AREA Step Checklist: Use the foilowing table to trackthe completion of each step: 1. Maintain/follow EDI setup procedures. 2.Maintain/follow EDI web setup procedures. Approval status: Edit history:

In step 238, service delivery center (SDC) ongoing support, help deskfunctions that are supplied to the client through time. This coversproblem reporting, new requests for reports, education questions, and soforth.

In step 240, the transition management team accesses detail tasktemplate PD54, Table 31, in the course of insuring that the humanresources aspects of the transition plan are in place and in progress.Specifically, this step deals with organizational impacts, changes inroles and responsibilities, labor relations, bonuses and incentives,meetings, feedback and comments. During this step, the auditors check tosee the plan is being executed properly. Template PD54 provides, eitherdirectly or by way of links to other documents, instructions, flowcharts, sample questionnaires, report models and checklists for guiding,coordinating and documenting the work of the transition management teamthrough the steps of this task during deployment and ongoing supportstages 104 and 105.

TABLE 31 DETAIL TASK: MANAGE HUMAN RESOURCES ACTIVITIES CREATION STATUSCategory: Transition Management Team: Transition Management Offeringtype: Req/Cat, SAF, Req/Cat&SAP Stage: 4. Deploy IMPORTANCE BUTTONSEducation: Yes Certification: Yes Auditable: Yes Critical path: NoIMPLEMENTATION Executed by: Service provider Performed by: Transitionmanager DETAIL TASK DETAILS Description: This step specifically focuseson the Human Resources aspects of the transition and is intended toinsure the elements of the transition plan that focus on this area arein place and in progress. During this detail task, you will be assessingand ensuring the steps in the plan are being implemented and thetransition is moving forward from an HR perspective. Specifically, thisstep will deal with the following areas. Organizational impacts Changesin roles and responsibilities Labor relations Bonuses/IncentivesMeetings/Feedback/Comments Earlier the client was assessed as to theimpact of the transition on these areas. A plan was developed to respondto the issues related to HR and built in the transition plan. Duringthis step, you will check to see the plan is being executed While it isthe responsibility of the Transition Management coordinator at theEnterprise/Service Provider project to ensure these tasks are completed,the client HR department must play a strong role to ensure the actionsrequired of the client are carried out In general, issues and concernsidentified will be handled with the right communications and trainingfor those affected. However, there may be cases where actions need to betaken that is specific to a particular problem. This is particularlytrue where jobs are either eliminated or added. Prerequisites: Ensure aclear understanding of the client various HR worksheets and the analysisof the sheets as part of the development of the transition pian. Go-liveis completed and the system/process has been successfully implemented.Deliverables: Updated input to the client Transition Management Plan,only as needed. Any required announcement material CustomizedPresentations for Meetings Methodology attachments: OrganizationAnnouncement Presentation -> PROJECT REFERENCE AREA Step StatusChecklist: Step Status 1. Ensure steps are in progress to move towardany changes in organization that are part of the transition. 2. Ensureany changes in organizational communications or relationships are inprogress. 3. Ensure changes in individual job roles and responsibilitiesfor managers/administration/ process end users 4. Ensure activitiesassociated with the loss of a job role are in place For any activitiesdirectly related to labor unions see next step document 5. Make sure thenew measurements (if any) are in place and understood by those affectedby the change. Ensure the transition to the new measurement system is ontract and any measurement that will affect peoples performanceevaluation are understood and working properly. Ensure normal businessreporting is working and those receiving the reports understand eachreport AND what they should be doing with each report. Ensure thetransition to the new measurement system is on track and any reports ormeasurements that will affect employee bonus plans are understood andworking properly. 6. Review the transition management plan for allelements associated with HR and HR impacts and ensure they are on trackfor completion by general cut over date. 7. Ensure the action plansidentified are provided as input and are included as an attachment thatupdates the final Transition Management Plan for the client. 8. Ensureuser meetings are scheduled. Review initial communications plan toensure that no changes are necessary to the base plan. After themeetings, provide a mechanism for feedback and comments. Approvalstatus: Edit history:

In step 242, the transition management team accesses detail tasktemplate PD81 in the course of distributing and analyzing a surveyquestionnaire and preparing action plans for implementation bymanagement. Template PD81 provides, either directly or by way of linksto other documents, instructions, flow charts, sample questionnaires,report models and checklists for guiding, coordinating and documentingthe work of the transition management team through the steps of thetask.

In step 244, the project office team accesses summary task P9C and itssubsidiary tasks in the course of providing post implementation QAreview. Template P9C provides, either directly or by way of links toother documents, instructions, flow charts, sample questionnaires,report models and checklists for guiding, coordinating and documentingthe work of the project office team through the steps of the task.

Advantages over the Prior Art

It is an advantage of the invention that there is provided a system andmethod for evaluating a client's general procurement and accountspayable (GP/AP) system.

It is an advantage of the invention that there is provided an optimizedsolution for out-sourcing procurement of goods and services.

It is an advantage of the invention that there is provided a system andmethod for training service providers.

It is an advantage of the invention that there is provided a system andmethod for managing service providers to assure quality of service.

It is an advantage of the invention that there is provided a system andmethod for managing a project.

It is an advantage of the invention that there is provided an optimizedgeneral procurement and accounts payable system characterized by lowercosts, a paperless process, and more comprehensive service with ashorter cycle time.

Alternative Embodiments

It will be appreciated that, although specific embodiments of theinvention have been described herein for purposes of illustration,various modifications may be made without departing from the spirit andscope of the invention. In particular, it is within the scope of theinvention to provide a computer program product or program element, or aprogram storage or memory device such as a solid or fluid transmissionmedium, magnetic or optical wire, tape or disc, or the like, for storingsignals readable by a machine, for controlling the operation of acomputer according to the method of the invention and/or to structureits components in accordance with the system of the invention.

Further, each step of the method may be executed on any generalcomputer, such as an IBM System 390, AS/400, PC or the like and pursuantto one or more, or a part of one or more, program elements, modules orobjects generated from any programming language, such as C++, Java,Pl/1, Fortran or the like. And still further, each said step, or a fileor object or the like implementing each said step, may be executed byspecial purpose hardware or a circuit module designed for that purpose.

Accordingly, the scope of protection of this invention is limited onlyby the following claims and their equivalents.

We claim:
 1. In a system for effecting through presales, assessment,preparation, development, deployment and support stages a transitionfrom a legacy process to an integrated, cross-functional generalprocurement and accounts payable application, a general procurement andaccounts payable application support system, comprising: a server; astorage device connected to said server; a plurality of team terminals;a communication link interconnecting said server and said terminals;said server maintaining a database of templates on said storage devicedescribing procedures and providing data fields for collecting data forsupporting said application; displaying at said team terminals in aplaybook summary view a create a summary task selection button, a createa detailed task button, a folders and views section, a task titledisplay and selection area; responsive to member selection of saidsummary tasks selection button presenting in said selection area alisting of support stage tasks organized by categories, said categoriesincluding information technology, project management, and transitionmanagement; responsive to user selection of said information technologycategory, presenting in said selection area a first listing of supportstage tasks and responsive to user selection of a support stage taskfrom said first listing presenting to said user a first task template;said user, responsive to said first task template, refining andexecuting production support for system management; responsive to userselection of said project management category, presenting in saidselection area a listing of support stage tasks for post-implementationquality assurance review and project support review; responsive to userselection of said transition management category, presenting in saidselection area a third listing of support stage tasks and responsive touser selection of a support stage task from said third listingpresenting to said user a third task template; said user, responsive tosaid third task template, executing support stage tasks for providingcommunication support, validating transition management support, andperforming post implementation survey support; and said templates beingserved to said users for operating said terminals for coordinating,recording, and tracking team activities; and said users responsive tosaid templates coordinating and tracking user education, survey andquality auditing procedures with respect to said general procurement andaccounts payable application.
 2. The system of claim 1, each saidtemplate storing, either directly or by way of links to other documents,one or more instructions, flow charts, sample questionnaires, reportmodels and checklists for guiding, coordinating and documenting the workof said enterprise teams.
 3. The system of claim 1, further comprising:said server being operable for maintaining a plurality of databases onsaid storage device customized to applications for a plurality ofcustomers of an enterprise for serving to said team terminals.
 4. Amethod for providing ongoing support for a general procurement andaccounts payable application of a customer of an enterprise, comprisingthe steps of: maintaining a database of templates for describingprocedures to a user and collecting information from said user forsupporting an operational general procurement and accounts payablesystem; operating a plurality of web-enabled user terminals to accessvia a server said database for receiving instructions and gathering saidinformation to coordinate user education, survey and quality auditingtasks by a plurality of enterprise teams implementing said ongoingsupport for said operational general procurement and accounts payableapplication; displaying to said user at said team terminals in aplaybook summary view a create a summary task selection button, a createa detailed task button, a folders and views section, a task titledisplay and selection area; responsive to user selection of a tasksselection button presenting in said selection area a listing of supportstage tasks organized by categories, said categories includinginformation technology, project management, and transition management;responsive to user selection of said information technology category,presenting in said selection area a first listing of support stage tasksand responsive to user selection of a support stage task from said firstlisting presenting to said first user a first task template; said user,responsive to said first task template, selectively refining andexecuting production support for system management; responsive to userselection of said project management category, presenting in saidselection area a second listing of support stage tasks and responsive touser selection of a support stage task from said second listingpresenting to said user a second task template; said user, responsive tosaid second task template, executing post-implementation qualityassurance review and project support review; responsive to userselection of said transition management category, presenting in saidselection area a third listing of support stage tasks and responsive touser selection of a support stage task from said third listingpresenting to said user a third task template; said user, responsive tosaid third task template, selectively executing communication support,validating transition management support, and performing postimplementation survey support.
 5. The method of claim 4, each saidtemplate storing, either directly or by way of links to other documents,one or more instructions, flow charts, sample questionnaires, reportmodels and checklists for guiding, coordinating and documenting the workof said enterprise teams.
 6. In a system for effecting throughassessment, preparation, development, deployment, and support stages atransition from a legacy process to an integrated, cross-functionalgeneral procurement and accounts payable application of a customer of anenterprise, an ongoing support system, comprising: a server; a storagedevice connected to said server; a plurality of team terminals; acommunication link interconnecting said server and said terminals; saidserver maintaining a database on said storage device of templatesdescribing procedures for supporting said integrated, cross-functionalgeneral procurement and accounts payable application; displaying at saidteam terminals in a playbook summary view a create a summary taskselection button, a create a detailed task button, a folders and viewssection, a task title display and selection area; responsive to userselection of a tasks selection button presenting in said selection areaa listing of support stage tasks organized by categories, saidcategories including information technology, project management, andtransition management; responsive to user selection of said Informationtechnology category, presenting in said selection area a first listingof support stage tasks and responsive to user selection of a supportstage task from said first listing Presenting to said user a first tasktemplate; said user, responsive to said first task template, refiningand executing production support for system management; responsive touser selection of said project management category, presenting in saidselection area a second listing of support stage tasks and responsive touser selection of a support stare task from said second listingpresenting to said user a second task template; said user, responsive tosaid second task template, executing support stage tasks forpost-implementation quality assurance review and project support review;and responsive to user selection of said transition management category,presenting in sale selection area a third listing of support stage tasksand responsive to user selection of a support stage task from said thirdlisting presenting to said user a third task template; said user,responsive to said third task template, selectively executing supportstare tasks for providing communication support, validating transitionmanagement support, and performing post implementation survey support;thereby coordinating, recording and tracking customer and enterpriseteams activities with respect to said support stage to provide atransition from said assessment, preparation, development, anddeployment stages to said support stage of said general procurement andaccounts payable application.
 7. The system of claim 6, each saidtemplate storing, either directly or by way of links to other documents,one or more instructions, flow charts, questionnaires, report models andchecklists for guiding, coordinating and documenting the work of saidenterprise teams.
 8. A method for integrating assessment, preparation,development, deployment, and support stages for a general procurementand accounts payable system using electronic requisitions, comprisingthe steps of: maintaining a database of templates for describingprocedures and collecting application descriptive and controlinformation for assessing, preparing, developing, deploying andsupporting said general procurement and accounts payable system;operating a plurality of web-enabled user terminals to access via aserver said database for scheduling tasks and collecting data by aplurality of teams implementing said procedures; displaying at said teamterminals in a playbook summary view a create a summary task selectionbutton, a create a detailed task button, a folders and views section, atask title display and selection area; responsive to member selection ofa tasks selection button presenting in said selection area a listing ofsupport stage tasks organized by categories, said categories includinginformation technology, project management, and transition management;responsive to member selection of said information technology category,presenting in said selection area a first listing of support stage tasksand responsive to user selection of a support stage task from said firstlisting presenting to said user a first task template; said user,responsive to said first task template, refining and executingproduction support for system management; responsive to member selectionof said project management category, presenting in said selection area asecond listing of support stage tasks and responsive to user selectionof a support stage task from said second listing presenting to said usera second task template; said user, responsive to said second tasktemplate, executing post-implementation quality assurance review andproject support review; and responsive to member selection of saidtransition management category, presenting in said selection area athird listing of support stage tasks and responsive to user selection ofa support stage task from said third listing presenting to said user athird task template; said user, responsive to said third task template,executing communication support, validating transition managementsupport, and performing post implementation survey support.
 9. Themethod of claim 8, each sand template storing, either directly or by wayof links to other documents, one or more instructions, flow charts,questionnaires, report models and checklists for guiding, coordinatingand documenting the work of said enterprise teams.
 10. A system forintegrating technical team and transition management personnel duringdesign and deployment stages including assessment, preparation,development, deployment, and support stages of a general procurement andaccounts payable application, comprising: a database server, a front endserver, a an accounting system server, a firewall, a plurality of team,terminals, a database store, an accounting system store, a communicationlink interconnecting said server and said terminals; said serverdisplaying at said team terminals in a playbook summary view a create asummary task selection button, a create a detailed task button, afolders and views section, a task title display and selection area;responsive to user selection of a tasks selection button presenting insaid selection area a listing of support stage tasks organized bycategories, said categories including information technology, projectmanagement, and transition management; responsive to user selection ofsaid information technology category, presenting in said selection areaa first listing of support stage tasks and responsive to user selectionof a support stage task from said first listing presenting to said usera first task template; said user, responsive to said first tasktemplate, executing production support for system management; responsiveto user selection of said project management category, presenting insaid selection area a second listing of support stage tasks andresponsive to user selection of a support stage task from said secondlisting presenting to said user a second task template; said user,responsive to said second task, template, executing support stare tasksfor post-implementation quality assurance review and project supportreview; responsive to user selection of said transition managementcategory, presenting in said selection area a third listing of supportstage tasks and responsive to user selection of a support stare taskfrom said third listing presenting to said user a third task template;said user, responsive to said third task template, selectively executingsupport stage tasks for providing communication support, validatingtransition management support, and performing post implementation surveysupport.
 11. The system of claim 10, said technical team and transitionmanagement personnel accessing said templates for receiving instructionsand collecting and sharing information for assessing, preparing,developing, deploying and supporting said general procurement andaccounts payable application.
 12. The system of claim 10, said technicalteam and transition management personnel accessing said templates forreceiving instructions and collecting and sharing information related toassessment, business controls, configuration, education, image,information technology, marketing, process, project management, frontend server, accounting system server, testing, and transitionmanagement.
 13. A system for customizing through presales, assessment,preparation, development, deployment, and support stages a transitionfrom a legacy process to an integrated general procurement and accountspayable application for each of a plurality of customers, comprising: aserver; a storage device connected to said server; a plurality ofterminals; a communication link interconnecting said server and saidterminals; said server (1) maintaining a database on said storage deviceof master templates describing procedures for assessing, preparing,developing, deploying and supporting each of said applications and (2)serving said master templates to members of enterprise teams operatingsaid terminals for personalizing for each of said plurality of customersa unique database of templates for use through presales, assessment,preparation, development, deployment, and support stages of said generalprocurement and accounts payable application; and further during saidsupport stage displaying at said team terminals in a playbook summaryview a create a summary task selection button, a create a detailed taskbutton, a folders and views section, a task title display and selectionarea; responsive to member selection of a tasks selection buttonpresenting in said selection area a listing of support stage tasksorganized by categories, said categories including informationtechnology, project management, and transition management; responsive tomember selection of said information technology category, presenting insaid selection area a first listing of support stage tasks andresponsive to member selection of a support stage task from said firstlisting presenting to said member a first task template; said member,responsive to said first task template, refining and executingproduction support for system management; responsive to member selectionof said project management category, presenting in said selection area asecond listing of support stage tasks and responsive to user selectionof a support stare task from said second listing presenting to saidmember a second Bask template; said member, responsive to said secondtask template, executing support stage tasks for post-implementationquality assurance review and project support review; and responsive tomember selection of said transition management category, presenting insaid selection area a third listing of support stage tasks andresponsive to user selection of a support stare task from said thirdlisting presenting to said member a third task template; said member,responsive to said third task template, selectively executing supportstare tasks for providing communication support, validating transitionmanagement support, and performing post implementation survey support.14. The system of claim 13, said members of enterprise teams accessingsaid templates for receiving instructions and collecting and sharinginformation for coordinating team activities with respect topersonalizing said unique database of templates for a customerapplication of a general procurement and accounts payable applicationincluding assessment, preparation, development, deployment and supportstages.
 15. A system for providing continuing support to a customer'sgeneral procurement and accounts payable application by enterprise teamswhich design and deploy said application, comprising: a database server;a storage device connected to said server; a plurality of teamterminals; an accounting system for implementing said application; afront end server connected to said accounting system through a firewall;a communication link interconnecting said database server, said frontend server, and said terminals; said database server maintaining adatabase of templates on said storage device describing procedures forsupporting said application and serving said templates to enterpriseteam members operating said terminals for coordinating, recording, andtracking team activities executing said procedures by displaying at saidteam terminals in a playbook summary view a create a summary taskselection button, a create a detailed task button, a folders and viewssection, a task title display and selection area; responsive to memberselection of a tasks selection button presenting in sand selection areaa listing of support stage tasks organized by categories, saidcategories including information technology, project management, andtransition management; responsive to member selection of saidinformation technology category, presenting in said selection area afirst listing of support stage tasks and responsive to user selection ofa support stage task from said first listing presenting to said member afirst task template; said member, responsive to said first tasktemplate, refining and executing production support for systemmanagement; responsive to member selection of said project managementcategory, presenting in said selection area a second listing of supportstage tasks and responsive to user selection of a support stare taskfrom said second listing presenting to said user a second task template;said user, responsive to said second task template, executing supportstage tasks for post-implementation quality assurance review and projectsupport review; and responsive to member selection of said transitionmanagement category, presenting in said selection area a third listingof support stage tasks and responsive to member selection of a supportstage task from said third listing presenting to said member a thirdtask template; said member, responsive to said third task template,selectively executing support stage tasks for providing communicationsupport, validating transition management support, and performing postimplementation survey support.
 16. A system for training and assessingthe quality of service provided by a general procurement and accountspayable service provider to a customer of an enterprise, comprising: aserver; a storage device connected to said server; a plurality of teamterminals; a communication link interconnecting said server and saidterminals; said server maintaining a database on said storage device oftemplates including data fields and describing procedures forpresentation to enterprise teams; said enterprise teams, responsive tosaid templates, or training said service provider and assessing thequality of service provided with respect to the general procurement andaccounts payable application of said customer; serving said templates toenterprise team members operating said terminals; and responsive toinput to said data fields a: said terminals by said enterprise teams,updating said database to provide an assessment of the quality ofservice provided by said service provider to said customer; displayingat said team terminals in a playbook summary view a create a summarytask selection button, a create a detailed task button, a folders andviews section, a task title display and selection area; responsive tomember selection of a tasks selection button presenting in saidselection area a listing of support stage tasks organized by categories,said categories including project management and transition management;responsive to member selection of said project management category,presenting in said selection area a first listing of support stage tasksand responsive to user selection of a support stage task from saidsecond listing presenting to said user a first task template; said user,responsive to said first task template, executing support stave tasksfor post-implementation quality assurance review and project supportreview; and responsive to member selection of said transition managementcategory, presenting in said selection area a second listing of supportstage tasks and responsive to member selection of a support stage taskfrom said second listing presenting to said member a second tasktemplate; said user, responsive to said second task template,selectively executed no support stave tasks for providing communicationsupport, validating transition management support, and performing postimplementation survey support; thereby coordinating, recording andtracking enterprise and service provider team activities with respect tosaid general procurement and accounts payable application.
 17. A programstorage device readable by a machine, tangibly embodying a program ofinstructions executable by a machine to perform method steps forproviding ongoing support for a general procurement and accounts payableapplication, said method steps comprising: maintaining a database oftemplates for describing procedures to a user and collecting informationfrom said user for supporting an operational general procurement andaccounts payable system; operating a plurality of web-enabled userterminals to access via a server said database for receivinginstructions and gathering said information to coordinate usereducation, survey and quality auditing tasks by a plurality ofenterprise teams implementing said ongoing support for said operationalgeneral procurement and accounts payable application; displaying to saiduser at said tear terminals in a playbook summary view a create asummary task selection button, a create a detailed task button, afolders and views section, a task title display and selection area;responsive to user selection of a tasks selection button presenting insaid selection area a listing of support stage tasks organized bycategories, said categories including information technology, projectmanagement, and transition management; responsive to user selection ofsaid information technology category, presenting in said selection areaa first listing of support stage tasks and responsive to user selectionof a subpart stage task from said first listing presenting to said usera first task template; said user, responsive to said first tasktemplate, selectively refining and executing production support forsystem management; responsive to user selection of said projectmanagement category, presenting in said selection area a second listingof support stage tasks and responsive to user selection of a supportstage task from said second listing presenting to said user a secondtask template; said user, responsive to said second task template,executing post-implementation quality assurance review and projectsupport review; and responsive to user selection of said transitionmanagement category, presenting in said selection area a third listingof support stage tasks and responsive to user selection of a supportstage task from said third listing presenting to said user a third tasktemplate; said user, responsive to said third task template selectivelyexecuting communication support, validating transition managementsupport, and performing post implementation survey support.
 18. Anarticle of manufacture comprising: a computer useable medium havingcomputer readable program code means embodied therein for providingongoing support for a general procurement and accounts payableapplication, the computer readable program means in said article ofmanufacture comprising: computer readable program code means for causinga computer to effect maintaining a database of templates or describingprocedures and collecting information for supporting an operationalgeneral procurement and accounts payable system; and computer readableprogram code means for causing a computer to effect operating aplurality of web-enabled user terminals to access via a server saiddatabase for receiving instructions and gathering said information tocoordinate user education, survey and quality auditing tasks by aplurality of enterprise teams implementing said ongoing support for saidoperational general procurement and accounts payable application;computer readable program code means for causing a computer to effectdisplaying to a member at said team terminals in a playbook summary viewa create a summary task selection button, a create a detailed taskbutton, a folders and views section, a task title display and selectionarea; computer readable program code means for causing a computer toeffect responsive to member selection of a tasks selection buttonpresenting in said selection area a listing of support stage tasksorganized by categories, said categories including informationtechnology, project management, and transition management; computerreadable program code means for causing a computer to effect responsiveto member selection of said information technology category, presentingin said selection area a first listing of support stage tasks, saiduser, responsive to a task presented in said first listing, refining andexecuting production support for system management; computer readableprogram code means for causing a computer to effect responsive to memberselection of said project management category, presenting in saidselection area a second listing of support stage tasks, said user,responsive to tasks presented in said second listings, performingpost-implementation quality assurance review and project support review;computer readable program code means for causing a computer to effectresponsive to member selection of said transition management category,presenting in said selection area a third listing of support stagetasks, said member, responsive to tasks presented in said third listing,providing communication support, validating transition managementsupport, and performing post implementation survey support; and computerreadable program code means for causing a computer to effect responsiveto user selection of a task, presenting at said team terminal a tasktemplate including data fields for member input of indicia selectivelydescriptive of said support stage tasks for presentation to said users.19. A program storage device readable by a machine, tangibly embodying aprogram of instructions executable by a machine to perform method stepsfor integrating assessment, preparation, development, deployment, andsupport stages for a general procurement and accounts payable systemusing electronic requisitions, said method steps comprising: maintaininga database of templates describing procedures for assessing, preparing,developing, deploying and supporting said general procurement andaccounts payable system; operating a plurality of web-enabled userterminals to access via a server said database responsive to saidtemplates for recording data with respect to assessment, preparation,development, deployment, and support stages by a plurality of teamsimplementing said procedures; displaying at said team terminals in aplaybook summary view a create a summary task selection button, a createa detailed task button, a folders and views section, a task titledisplay and selection area; responsive to member selection of a tasksselection button presenting in said selection area a listing of supportstage tasks organized by categories, said categories includinginformation technology, project management, and transition management;responsive to member selection of said information technology category,presenting in said selection area a first listing of support stagetasks; said member, responsive to a support stage task from said firstlisting, refining and executing production support for systemmanagement; responsive to member selection of said project managementcategory, presenting in said selection area a second listing of supportstage tasks; said member, responsive to a support stage task from saidsecond listing, performing post-implementation quality assurance reviewand project support review; responsive to member selection of saidtransition management category, presenting in said selection area athird listing of support stage tasks; said member, responsive to asupport stage task from said third listing, providing communicationsupport, validating transition management support, and performing postimplementation survey support; and responsive to user selection of atask, presenting at said team terminal a task template including datafields, said user entering to said data fields indicia selectivelydescriptive of said support stage tasks.
 20. An article of manufacturecomprising: a computer useable medium having computer readable programcode means embodied therein for integrating assessment, preparation,development, deployment, and support stages for a general procurementand accounts payable system using electronic requisitions, the computerreadable program means in said article of manufacture comprising:computer readable program code means for causing a computer to effectmaintaining a database of templates describing procedures and providingdata fields for assessing, preparing, developing, deploying andsupporting said general procurement and accounts payable system;computer readable program code means for causing a computer to effectoperating a plurality of web-enabled user terminals to access via aserver said database for coordinating tasks and receiving data to saiddata fields by a plurality of teams implementing said procedures;computer readable program code means for causing a computer to effectdisplaying at said team terminals in a playbook summary view a create asummary task selection button, a create a detailed task button, afolders and views section, a task title display and selection area;computer readable program code means for causing a computer to effectresponsive to member selection of a tasks selection button presenting insaid selection area a listing of support stage tasks organized bycategories, said categories including information technology, projectmanagement, and transition management; computer readable program codemeans for causing a computer to effect responsive to member selection ofsaid information technology category, presenting in said selection areaa first listing of support stage tasks; said member, responsive to saidfirst listing, refining and executing production support for systemmanagement; computer readable program code means for causing a computerto effect responsive to member selection of said project managementcategory, presenting in said selection area a second listing of supportstage tasks; said member, responsive to said second listing, executingpost-implementation quality assurance review and project support review;computer readable program code means for causing a computer to effectresponsive to member selection of said transition management category,presenting in said selection area a third listing of support stagetasks; said member, responsive to said third listing, providingcommunication support, validating transition management support, andperforming post implementation survey support; and computer readableprogram code means for causing a computer to effect responsive to userselection of a task, presenting at said team terminal a task templateincluding data fields; said user Providing input of indicia selectivelydescriptive of said support stage tasks for subsequent presentation tosaid users; thereby integrating assessment, preparation, development,deployment, and support stages for said general procurement and accountspayable system.
 21. A computer program product or computer programelement for integrating assessment, preparation, development,deployment, and support stages for a general procurement and accountspayable system using electronic requisitions according to the steps of:maintaining a database of templates describing procedures and providingfor data collection for assessing, preparing, developing, deploying andsupporting said general procurement and accounts payable system;operating a plurality of web-enabled user terminals to access via aserver said database for coordinating tasks by and receiving data from aplurality of teams implementing said procedures; displaying at said teamterminals in a playbook summary view a create a summary task selectionbutton, a create a detailed task button, a folders and views section, atask title display and selection area; responsive to member selection ofa tasks selection button presenting in said selection area a listing ofsupport stage tasks organized by categories, said categories includinginformation technology, project management, and transition management;responsive to member selection of said information technology category,presenting in said selection area a first listing of support stagetasks; said member, responsive to tasks from said first listing,refining and executing production support for system management;responsive to member selection of said project management category,presenting in said selection area a second listing of support stagetasks; said member, responsive to tasks from said second listing,executing post-implementation quality assurance review and projectsupport review; responsive to member selection of said transitionmanagement category, presenting in said selection area a third listingof support stage tasks; said member, responsive to tasks from said thirdlisting, providing communication support, validating transitionmanagement support, and performing post implementation survey support;and responsive to user selection of a task, presenting at said teamterminal a task template including data fields; said user entering inputof indicia selectively descriptive Of said support stage; therebyintegrating said assessment, preparation, development, deployment, andsupport stages for said general procurement and accounts payable system.